home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Dr. Windows 3
/
dr win3.zip
/
dr win3
/
UTILITY1
/
CBWLITE.ZIP
/
README.TXT
< prev
Wrap
Text File
|
1993-11-01
|
19KB
|
326 lines
Colorado Backup for Windows /Lite Edition
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To install CBWLITE, please follow the following steps:
1) Download CBWLITE.ZIP (or CBWLITE.EXE) to a directory
called CMS.
2) Run PKUNZIP or type CBWLITE to decompress the files.
Note: Error 7AF
You cannot install CBWLITE from C: to C:.
The install files MUST be on a different Drive.
Please see Step (3) for an explanation.
3) If you have only one partition, for example C:, then
you must copy the decompressed files to either a Floppy
disk or create a SUBSTituted drive (For Advanced users only).
*** We recommend uncompressing the archive to a floppy.
For example, PKUNZIP cbwlite.zip a:\
Below is the DOS reference on how to create a SUBST drive.
------------------------------------------------------------
SUBST
Associates a path with a drive letter.
The drive letter you assign represents a virtual drive,
because you can use the drive letter in commands as if it
were a physical drive. Do not use the SUBST command when you
are running Windows.
Syntax
SUBST [drive1: [drive2:]path]
SUBST drive1: /D
SUBST d: c:\CMS
To display the names of the virtual drives in effect, use the following
syntax:
SUBST
Parameters
drive1:
Specifies the virtual drive to which you want to assign a path.
drive2:
Specifies the physical drive that contains the specified path (if
different from the current drive).
path
Specifies the path that you want to assign to a virtual drive.
Switch
/D
Deletes a virtual drive.
Related Command
For information about increasing the number of available drive letters,
see the <LASTDRIVE> command.
------------------------------------------------------------------------
4) If you have multiple partitions, Please copy the
decompressed files to another drive.
5) Run install.exe from within Windows.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Colorado Backup for Windows Troubleshooting
Version 1.10 Revision 1.10d
Contents
1.0 Additional Information.
1.1 Sound Boards.
1.2 Fax Modems and Voice Mail Systems
1.3 Third Party Windows Backup Software.
2.0 Trouble Shooting.
2.1 General Protection Fault.
3.0 Performance Tips.
3.1 Video Drivers.
3.2 Operating CBW in the background.
3.3 Memory and Resources.
4.0 Considerations for Network Users
5.0 General Trouble Shooting Hints
1.0 Additional Information.
1.1 Sound Boards
Using a sound board with CBW may require special consideration
to avoid interrupt and DMA conflicts. This is particularly
true when dealing with the Trakker tape drive unit. Most
sound boards use an interrupt that corresponds with a parallel
port. If a Trakker unit is connected to one of these parallel
ports, you may have poor sound quality and system lockups.To correct
this, choose an interrupt for the sound board that is different from
your parallel port. See your sound board's documentation for
instructions.
Some sound boards install device drivers that conflict with
CBW's device driver, CMSWTAPE.386. These sound board device
drivers install MIDI support. If you are experiencing
problems with CBW, you might have a conflict with these MIDI
drivers. To correct this, you can remove the MIDI support
from the Drivers entry in the Control Panel in Windows. See
your sound board's documentation for instructions.
1.2 Fax Modems and Voice Mail Systems.
Some fax modems and voice mail systems install device drivers
under Windows that may conflict with CBW. Symptoms of this
problem include having the tape backup software produce an
error message when a fax or voice mail is received. To
correct this, disable the fax or voice mail reception either
through the control panel or through the control program for
your board.
1.3 Third Party Windows Backup Software.
Most third party backup programs for Windows install a device
driver that conflicts with the CBW driver. If any other
backup software has been installed through Windows, you may
need to remove these drivers before CBW will operate. To do
this, you will need to edit the SYSTEM.INI file in your
Windows directory. Under the section [386enh] you should see
several lines that read 'DEVICE='. If any of these lines reference
'VIRWT.386', 'VITD.386', 'MYBACKUP.386', 'VFINTD.386',
'CPBVXD.386', or 'FASTBACK.386', you will need to add a
semicolon to the beginning of these lines. Common symptoms of a
drive conflict are error 61B or lockups.
2.0 Troubleshooting.
2.1 General Protection Fault.
In some situations, CBW may fail with a message indicating
that a General Protection Fault was detected. In situations
like this, the most common cause is having a parameter of the
EMM386.EXE device driver not properly set. To check for this
situation, edit the CONFIG.SYS file and place a remark, REM
before the DEVICE=EMM386.EXE line. Next, reboot the computer
and retry the CBW operation. If the error no longer occurs,
it is an indication that one of the parameters of the
EMM386.EXE line is conflicting. Try removing parameters one
at a time until the conflicting paramter is located. The Dos
manual contains an explanation of the EMM386.EXE and its
parameters.
If the error persists, or if you do not have a line with
EMM386.EXE, then we need to check for a device driver conflict
as stated in section 1.3. Occasionally device driver
conflicts can cause a General Protection Fault.
3.0 Performance Tips
3.1 Video Drivers
Some systems may experience slow backup speeds. On these
systems, improvements may be gained by changing from the
default VGA driver to the driver supplied with the video
board. To determine if this is the problem, start a backup,
then minimize the CBW window. It is normal for backup speeds
to improve somewhat with CBW minimized, however, if the
results are extreme it may be necessary to change the video
driver. See the video board manual for instructions.
3.2 Operating CBW in the background.
While CBW is capable of running on a system in the background,
performance may decline with each additional application
running. Memory is used by each application which could cause
CBW to fail with an out of memory error.
When running a backup operation in the background, some open
files may not back up.
For fastest performance and to assure a complete backup, you
may wish to operate CBW as the only application open on the
system.
3.3 Memory and Resources.
If you do not have sufficient memory or resources to execute
CBW you will receive an error message. However, having less
than 2.5M of available memory or less than 70% resources may
result in slow performance. If this is the case, you can
improve performance by making more memory or more resources
available to CBW.
To check your available memory, choose Help from the Program
Manager, and then choose About Program Manager. This screen
will provide you with the amount of memory and system
resources available.
To make more memory and resources available, you may need to
close other applications, minimize Program Manager, add more RAM,
or increase the size of your permanent/temporary swap file.
4.0 Considerations for Network Users.
Generally CBW works transparently with Windows for Workgroups,
NetWare Lite and Lantastic, however, with the current version
of CBW, specific file attributes, bindery and privilege
information will not be saved. Please refer to the Networks
Applications s